home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Supervisor's Toolkit
/
Network Supervisor's Toolkit.iso
/
novell
/
fyi8
/
08069.dos
< prev
Wrap
Text File
|
1996-07-10
|
3KB
|
48 lines
Number: F2TH072590U198
Subject: Connecting Ethernet II and 802.3
Date: August 2, 1990
- - - - - - - - - - - - - - - - - - - - - - - -
GENERAL
INFORMATION: The diagram below is an example. We've got an existing
"flat" network of 286 and 386 systems (w/ 802.3 packets).
The customer is planning to add a NetWare for VMS server
(using Eth II packets) and confuse this "big" network with
packet types.
If we add a NetWare 386 server (v3.1) to this network with
2 Ethernet cards, one using 802.3 and one using Ethernet II,
then that server could communicate with both sides. The
real question is if there were workstations that wanted to
see ALL servers, could they use DOS ODI drivers and accept
both 802.3 AND Ethernet II packets concurrently?
Of course the two packet types would be coursing around the
network but wouldn't they effectively ignore one another?
Couldn't they both be saying they were the same network
address?
Any thoughts or arguments?
-----------------------------------------------------------------------------
If they haven't yet added the VAX to the wire, why not put
two wires in? You could put two cards in one server and
hang the VAX off it's own wire and only have to ECONFIG the
one card. You would then route through that server for
anyone needing the VAX. Otherwise, you may as well have
only one card in each server and ECONFIG everyone. You're
not going to have two cards in one server that will share
the same internet address even though they may be sending
different packet types.
-----------------------------------------------------------------------------
Unfortunately, under ODI, IPX will only bind itself to the
first packet type defined in the NET.CFG file (this was done
to save workstation memory). So you can't do it. But if
they are using v3.1 in the file server, you can load the LAN
driver twice on one card and have it support two packet
types. That way they don't need to have two cards in the
server.